Providing a system with access to a resource using a disposable email address

ABSTRACT

One or more computing devices, systems, and/or methods for providing a system with access to resources associated with a user account using a disposable email address (DEA) are provided. A request to provide a system with access to a first set of resources may be received. The first set of resources may be associated with a first email account associated with a first email address. A first DEA associated with the first email account may be generated. The first DEA may be transmitted to the system. A first set of modified emails may be generated based upon a first set of emails of the first email account. A first modified email of the first set of modified emails may comprise an indication of the first DEA. Access to the first set of modified emails may be provided to the system. The first DEA may be deactivated.

RELATED APPLICATION

This application claims priority to and is a continuation of U.S.application Ser. No. 16/374,008, filed on Apr. 3, 2019, entitled“PROVIDING A SYSTEM WITH ACCESS TO A RESOURCE USING A DISPOSABLE EMAILADDRESS”, which is incorporated by reference herein in its entirety.

BACKGROUND

Many systems, such as websites, price protection systems, contentplatforms, etc. may provide services using resources of an email accountassociated with an email service provider. For example, a first systemmay be authorized to access one or more resources of a first emailaccount and/or may be provided with access to personal information(e.g., email address, phone number, mailing address, etc.) associatedwith the first email account. As a result of the first system beingprovided with the access to the personal information, the personalinformation may be disclosed to entities without the first user'spermission and/or the personal information may be misused.

SUMMARY

In accordance with the present disclosure, one or more computing devicesand/or methods are provided. In an example, a request to provide asystem with access to a first set of resources may be received. Thefirst set of resources may be associated with a first email accountassociated with a first email address. A first disposable email address(DEA) associated with the first email account may be generated. Thefirst DEA may be transmitted to the system. Emails of the first emailaccount may be analyzed to identify a first set of emails associatedwith the request. A first set of modified emails may be generated basedupon the first set of emails. A first modified email of the first set ofmodified emails may comprise an indication of the first DEA. Access tothe first set of modified emails may be provided to the system. A firstemail may be received from the system. The first email may be addressedto a second email address. The first email may be indicative of thefirst DEA (e.g., a first sender address of the first email may beindicative of the first DEA). A second email may be generated based uponthe first email. The second email may be indicative of the first emailaddress (e.g., a second sender address of the second email may beindicative of the first email address). The second email may betransmitted to a second email account associated with the second emailaddress. The first DEA may be deactivated.

In an example, a graphical user interface of a first client deviceassociated with a first user account may be controlled to display aselectable input associated with providing a system with access to afirst set of resources associated with the first user account. A requestto provide the system with access to the first set of resources may bereceived via a selection of the selectable input. A first DEA associatedwith the first user account may be generated. The first DEA associatedwith the first user account may be transmitted to the system.

DESCRIPTION OF THE DRAWINGS

While the techniques presented herein may be embodied in alternativeforms, the particular embodiments illustrated in the drawings are only afew examples that are supplemental of the description provided herein.These embodiments are not to be interpreted in a limiting manner, suchas limiting the claims appended hereto.

FIG. 1 is an illustration of a scenario involving various examples ofnetworks that may connect servers and clients.

FIG. 2 is an illustration of a scenario involving an exampleconfiguration of a server that may utilize and/or implement at least aportion of the techniques presented herein.

FIG. 3 is an illustration of a scenario involving an exampleconfiguration of a client that may utilize and/or implement at least aportion of the techniques presented herein.

FIG. 4 is a flow chart illustrating an example method for providing asystem with access to one or more resources associated with a useraccount using a disposable email address (DEA).

FIG. 5A is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a graphical user interface of a firstclient device is controlled to display a first email interface.

FIG. 5B is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a graphical user interface of a firstclient device is controlled to display a first email.

FIG. 5C is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a graphical user interface of a firstclient device is controlled to display a consent interface.

FIG. 5D is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a request to provide a priceprotection system with access to resources associated with an accessscope is transmitted by a first server associated with the priceprotection system to a second server associated with an email system.

FIG. 5E is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a plurality of modified emails isgenerated based upon a plurality of emails of a first email account.

FIG. 5F is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a first modified email of a pluralityof modified emails is generated based upon a first email of a pluralityof emails.

FIG. 5G is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a graphical user interface of a firstclient device is controlled to display a first email interface.

FIG. 5H is a component block diagram illustrating an example system forproviding a system with access to one or more resources associated witha user account using a DEA, where a graphical user interface of a firstclient device is controlled to display a second email.

FIG. 6 is an illustration of a scenario featuring an examplenon-transitory machine readable medium in accordance with one or more ofthe provisions set forth herein.

DETAILED DESCRIPTION

Subject matter will now be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific example embodiments. Thisdescription is not intended as an extensive or detailed discussion ofknown concepts. Details that are known generally to those of ordinaryskill in the relevant art may have been omitted, or may be handled insummary fashion.

The following subject matter may be embodied in a variety of differentforms, such as methods, devices, components, and/or systems.Accordingly, this subject matter is not intended to be construed aslimited to any example embodiments set forth herein. Rather, exampleembodiments are provided merely to be illustrative. Such embodimentsmay, for example, take the form of hardware, software, firmware or anycombination thereof.

1. Computing Scenario

The following provides a discussion of some types of computing scenariosin which the disclosed subject matter may be utilized and/orimplemented.

1.1. Networking

FIG. 1 is an interaction diagram of a scenario 100 illustrating aservice 102 provided by a set of servers 104 to a set of client devices110 via various types of networks. The servers 104 and/or client devices110 may be capable of transmitting, receiving, processing, and/orstoring many types of signals, such as in memory as physical memorystates.

The servers 104 of the service 102 may be internally connected via alocal area network 106 (LAN), such as a wired network where networkadapters on the respective servers 104 are interconnected via cables(e.g., coaxial and/or fiber optic cabling), and may be connected invarious topologies (e.g., buses, token rings, meshes, and/or trees). Theservers 104 may be interconnected directly, or through one or more othernetworking devices, such as routers, switches, and/or repeaters. Theservers 104 may utilize a variety of physical networking protocols(e.g., Ethernet and/or Fiber Channel) and/or logical networkingprotocols (e.g., variants of an Internet Protocol (IP), a TransmissionControl Protocol (TCP), and/or a User Datagram Protocol (UDP). The localarea network 106 may include, e.g., analog telephone lines, such as atwisted wire pair, a coaxial cable, full or fractional digital linesincluding T1, T2, T3, or T4 type lines, Integrated Services DigitalNetworks (ISDNs), Digital Subscriber Lines (DSLs), wireless linksincluding satellite links, or other communication links or channels,such as may be known to those skilled in the art. The local area network106 may be organized according to one or more network architectures,such as server/client, peer-to-peer, and/or mesh architectures, and/or avariety of roles, such as administrative servers, authenticationservers, security monitor servers, data stores for objects such as filesand databases, business logic servers, time synchronization servers,and/or front-end servers providing a user-facing interface for theservice 102.

Likewise, the local area network 106 may comprise one or moresub-networks, such as may employ differing architectures, may becompliant or compatible with differing protocols and/or may interoperatewithin the local area network 106. Additionally, a variety of local areanetworks 106 may be interconnected; e.g., a router may provide a linkbetween otherwise separate and independent local area networks 106.

In the scenario 100 of FIG. 1 , the local area network 106 of theservice 102 is connected to a wide area network 108 (WAN) that allowsthe service 102 to exchange data with other services 102 and/or clientdevices 110. The wide area network 108 may encompass variouscombinations of devices with varying levels of distribution andexposure, such as a public wide-area network (e.g., the Internet) and/ora private network (e.g., a virtual private network (VPN) of adistributed enterprise).

In the scenario 100 of FIG. 1 , the service 102 may be accessed via thewide area network 108 by a user 112 of one or more client devices 110,such as a portable media player (e.g., an electronic text reader, anaudio device, or a portable gaming, exercise, or navigation device); aportable communication device (e.g., a camera, a phone, a wearable or atext chatting device); a workstation; and/or a laptop form factorcomputer. The respective client devices 110 may communicate with theservice 102 via various connections to the wide area network 108. As afirst such example, one or more client devices 110 may comprise acellular communicator and may communicate with the service 102 byconnecting to the wide area network 108 via a wireless local areanetwork 106 provided by a cellular provider. As a second such example,one or more client devices 110 may communicate with the service 102 byconnecting to the wide area network 108 via a wireless local areanetwork 106 provided by a location such as the user's home or workplace(e.g., a WiFi (Institute of Electrical and Electronics Engineers (IEEE)Standard 802.11) network or a Bluetooth (IEEE Standard 802.15.1)personal area network). In this manner, the servers 104 and the clientdevices 110 may communicate over various types of networks. Other typesof networks that may be accessed by the servers 104 and/or clientdevices 110 include mass storage, such as network attached storage(NAS), a storage area network (SAN), or other forms of computer ormachine readable media.

1.2. Server Configuration

FIG. 2 presents a schematic architecture diagram 200 of a server 104that may utilize at least a portion of the techniques provided herein.Such a server 104 may vary widely in configuration or capabilities,alone or in conjunction with other servers, in order to provide aservice such as the service 102.

The server 104 may comprise one or more processors 210 that processinstructions. The one or more processors 210 may optionally include aplurality of cores; one or more coprocessors, such as a mathematicscoprocessor or an integrated graphical processing unit (GPU); and/or oneor more layers of local cache memory. The server 104 may comprise memory202 storing various forms of applications, such as an operating system204; one or more server applications 206, such as a hypertext transportprotocol (HTTP) server, a file transfer protocol (FTP) server, or asimple mail transport protocol (SMTP) server; and/or various forms ofdata, such as a database 208 or a file system. The server 104 maycomprise a variety of peripheral components, such as a wired and/orwireless network adapter 214 connectible to a local area network and/orwide area network; one or more storage components 216, such as a harddisk drive, a solid-state storage device (SSD), a flash memory device,and/or a magnetic and/or optical disk reader.

The server 104 may comprise a mainboard featuring one or morecommunication buses 212 that interconnect the processor 210, the memory202, and various peripherals, using a variety of bus technologies, suchas a variant of a serial or parallel AT Attachment (ATA) bus protocol; aUniform Serial Bus (USB) protocol; and/or Small Computer SystemInterface (SCI) bus protocol. In a multibus scenario, a communicationbus 212 may interconnect the server 104 with at least one other server.Other components that may optionally be included with the server 104(though not shown in the schematic diagram 200 of FIG. 2 ) include adisplay; a display adapter, such as a graphical processing unit (GPU);input peripherals, such as a keyboard and/or mouse; and a flash memorydevice that may store a basic input/output system (BIOS) routine thatfacilitates booting the server 104 to a state of readiness.

The server 104 may operate in various physical enclosures, such as adesktop or tower, and/or may be integrated with a display as an“all-in-one” device. The server 104 may be mounted horizontally and/orin a cabinet or rack, and/or may simply comprise an interconnected setof components. The server 104 may comprise a dedicated and/or sharedpower supply 218 that supplies and/or regulates power for the othercomponents. The server 104 may provide power to and/or receive powerfrom another server and/or other devices. The server 104 may comprise ashared and/or dedicated climate control unit 220 that regulates climateproperties, such as temperature, humidity, and/or airflow. Many suchservers 104 may be configured and/or adapted to utilize at least aportion of the techniques presented herein.

1.3. Client Device Configuration

FIG. 3 presents a schematic architecture diagram 300 of a client device110 whereupon at least a portion of the techniques presented herein maybe implemented. Such a client device 110 may vary widely inconfiguration or capabilities, in order to provide a variety offunctionality to a user such as the user 112. The client device 110 maybe provided in a variety of form factors, such as a desktop or towerworkstation; an “all-in-one” device integrated with a display 308; alaptop, tablet, convertible tablet, or palmtop device; a wearable devicemountable in a headset, eyeglass, earpiece, and/or wristwatch, and/orintegrated with an article of clothing; and/or a component of a piece offurniture, such as a tabletop, and/or of another device, such as avehicle or residence. The client device 110 may serve the user in avariety of roles, such as a workstation, kiosk, media player, gamingdevice, and/or appliance.

The client device 110 may comprise one or more processors 310 thatprocess instructions. The one or more processors 310 may optionallyinclude a plurality of cores; one or more coprocessors, such as amathematics coprocessor or an integrated graphical processing unit(GPU); and/or one or more layers of local cache memory. The clientdevice 110 may comprise memory 301 storing various forms ofapplications, such as an operating system 303; one or more userapplications 302, such as document applications, media applications,file and/or data access applications, communication applications such asweb browsers and/or email clients, utilities, and/or games; and/ordrivers for various peripherals. The client device 110 may comprise avariety of peripheral components, such as a wired and/or wirelessnetwork adapter 306 connectible to a local area network and/or wide areanetwork; one or more output components, such as a display 308 coupledwith a display adapter (optionally including a graphical processing unit(GPU)), a sound adapter coupled with a speaker, and/or a printer; inputdevices for receiving input from the user, such as a keyboard 311, amouse, a microphone, a camera, and/or a touch-sensitive component of thedisplay 308; and/or environmental sensors, such as a global positioningsystem (GPS) receiver 319 that detects the location, velocity, and/oracceleration of the client device 110, a compass, accelerometer, and/orgyroscope that detects a physical orientation of the client device 110.Other components that may optionally be included with the client device110 (though not shown in the schematic architecture diagram 300 of FIG.3 ) include one or more storage components, such as a hard disk drive, asolid-state storage device (SSD), a flash memory device, and/or amagnetic and/or optical disk reader; and/or a flash memory device thatmay store a basic input/output system (BIOS) routine that facilitatesbooting the client device 110 to a state of readiness; and a climatecontrol unit that regulates climate properties, such as temperature,humidity, and airflow.

The client device 110 may comprise a mainboard featuring one or morecommunication buses 312 that interconnect the processor 310, the memory301, and various peripherals, using a variety of bus technologies, suchas a variant of a serial or parallel AT Attachment (ATA) bus protocol;the Uniform Serial Bus (USB) protocol; and/or the Small Computer SystemInterface (SCI) bus protocol. The client device 110 may comprise adedicated and/or shared power supply 318 that supplies and/or regulatespower for other components, and/or a battery 304 that stores power foruse while the client device 110 is not connected to a power source viathe power supply 318. The client device 110 may provide power to and/orreceive power from other client devices.

In some scenarios, as a user 112 interacts with a software applicationon a client device 110 (e.g., an instant messenger and/or electronicmail application), descriptive content in the form of signals or storedphysical states within memory (e.g., an email address, instant messengeridentifier, phone number, postal address, message content, date, and/ortime) may be identified. Descriptive content may be stored, typicallyalong with contextual content. For example, the source of a phone number(e.g., a communication received from another user via an instantmessenger application) may be stored as contextual content associatedwith the phone number. Contextual content, therefore, may identifycircumstances surrounding receipt of a phone number (e.g., the date ortime that the phone number was received), and may be associated withdescriptive content. Contextual content, may, for example, be used tosubsequently search for associated descriptive content. For example, asearch for phone numbers received from specific individuals, receivedvia an instant messenger application or at a given date or time, may beinitiated. The client device 110 may include one or more servers thatmay locally serve the client device 110 and/or other client devices ofthe user 112 and/or other individuals. For example, a locally installedwebserver may provide web content in response to locally submitted webrequests. Many such client devices 110 may be configured and/or adaptedto utilize at least a portion of the techniques presented herein.

2. Presented Techniques

One or more computing devices and/or techniques for providing a systemwith access to one or more resources associated with a user accountusing a disposable email address (DEA) are provided. For example, afirst user may want a first system to have access to one or more firstresources associated with a first user account associated with the firstuser. For example, the first user account may correspond to a firstemail account and/or the first system may correspond to one or more of anews system (e.g., a system configured to provide news content), ascheduling system (e.g., a system configured to provide schedulingservices), a purchase protection system (e.g., a system configured toprovide purchase protection services), a social network system, acommunication system (e.g., one or more of a messaging system, a videocalling system, an audio calling system, etc.), etc. In some examples,identification information associated with the first user account may betransmitted to the first system. For example, the identificationinformation may comprise one or more of a name of the first user (and/ora name associated with the first user account), a first usernameassociated with the first user account, a first email address associatedwith the first email account, a phone number associated with the firstuser account (and/or the first user), a mailing address associated withthe first user account (and/or the first user), etc. However, theidentification information may be misused and/or may be used in ways thefirst user does not approve and/or desire. For example, theidentification information may be disclosed to entities without thefirst user's permission, the identification information may be collectedand/or used for directing promotional content to the first user that thefirst user does not have an interest in, the first email accountassociated with the first user may be subscribed to one or moresubscription services without the first user's permission, etc.Alternatively and/or additionally, emails associated with the entitiesmay be transmitted to the first email account for an extended period oftime.

In accordance with one or more of the techniques presented herein, arequest to provide the first system with access to the one or more firstresources may be received. A first DEA associated with the first emailaccount may be generated. The first DEA may be transmitted to the firstsystem. For example, the identification information, comprising thefirst DEA, may be transmitted to the first system. Alternatively and/oradditionally, the identification information may not comprise the firstemail address and/or the first username. In some examples, the firstsystem may be provided with access to the one or more first resources.For example, the one or more first resources may comprise one or more ofone or more emails associated with the first email account, one or moresocial media posts associated with the first user account, etc. In someexamples, the first DEA may be deactivated. For example, the first DEAmay be deactivated responsive to receiving a request to deactivate thefirst DEA. Alternatively and/or additionally, the first DEA may bedeactivated responsive to a duration of time that the first DEA isactive meeting a threshold duration of time. In some examples,responsive to deactivating the first DEA, the first system may not beprovided with access to resources associated with the first useraccount.

An embodiment of providing a system with access to one or more resourcesassociated with a user account using a DEA is illustrated by an examplemethod 400 of FIG. 4 . A first user, such as user Jill, (e.g., and/or afirst client device associated with the first user) may access and/orinteract with one or more interfaces associated with a content system.For example, the one or more interfaces may correspond to one or more ofone or more applications (e.g., mobile applications) installed on thefirst client device, one or more websites accessed via a browser of thefirst client device, software installed on the first client device, etc.associated with the content system. Alternatively and/or additionally,each interface of the one or more interfaces may be associated with aservice, of one or more services, provided by the content system. Forexample, the content system may be an internet system providing the oneor more interfaces, where each interface of the one or more interfacesmay provide a service of the one or more services. Alternatively and/oradditionally, the first user may access and/or interact with the contentsystem using a first user account with the content system. In someexamples, the first user account may correspond to a first emailaccount.

In some examples, the content system may be associated with an emailservice provider for sending and/or receiving emails. For example, anemail interface of the one or more interfaces associated with thecontent system may be used to send and/or receive emails associated withthe first email account. Alternatively and/or additionally, the contentsystem may be associated with a communication service (and/or amessaging service, etc.) for performing communications via messaging,voice calls, video calls, etc. For example, a communication interface ofthe one or more interfaces associated with the content system may beused to send and/or receive messages and/or perform communications viaone or more of messaging, voice calls, video calls, etc. Alternativelyand/or additionally, the content system may be associated with a socialmedia service for social networking and/or posting social media posts.For example, a social media interface of the one or more interfacesassociated with the content system may be used to post social mediaposts, perform communications via messaging and/or connect with users ofthe social media service. Alternatively and/or additionally, the contentsystem may be associated with a scheduling service (e.g., the schedulingservice may be associated with an electronic calendar associated withthe first user account). For example, a scheduling interface of the oneor more interfaces associated with the content system may be used forscheduling events, meetings, etc. and/or for viewing holidays,occasions, receiving notifications indicative of upcoming events and/ormeetings, etc. Alternatively and/or additionally, the content system maybe associated with a search engine service for performing searches. Forexample, a search interface of the one or more interfaces associatedwith the content system may be used for performing searches based uponqueries. Alternatively and/or additionally, the content system may beassociated with a news content service for consuming, downloading and/orviewing news content (e.g., news videos, news articles, etc.). Forexample, a news content interface of the one or more interfacesassociated with the content system may be used for consuming,downloading and/or viewing news content. Alternatively and/oradditionally, the content system may be associated with a media platformvideo for consuming, downloading, uploading and/or viewing media (e.g.,videos, audio, etc.). For example, a media platform interface of the oneor more interfaces associated with the content system may be used forconsuming, downloading, uploading and/or viewing media (e.g., videos,audio, etc.).

In some examples, one or more resources associated with the first useraccount (and/or the first email account) may be used by one or moresystems. The one or more systems may be different than the contentsystem. Alternatively and/or additionally, the one or more systems maybe authorized (by the first user, the first client device and/or thecontent system) to access the one or more resources. Alternativelyand/or additionally, rather than disclosing personal information (suchas email addresses), a DEA may be generated for a system of the one ormore systems and/or the DEA may be used for system authorization (e.g.,the DEA may be used for logging into the system and/or for authorizingaccess to the one or more resources).

At 402, a first request to provide a second system with access to afirst set of resources may be received. For example, the first set ofresources may be associated with the first email account (and/or thefirst user account). In some examples, the first email account (and/orthe first user account) may be associated with a first email address(e.g., “jillhiggins@exampleemail.com”) and/or a first username (e.g.,“jillhiggins”). Alternatively and/or additionally, the second system maybe different than and/or separate from the content system (e.g., thesecond system may be an external third party system with respect to thecontent system).

In some examples, the first request may be received using a systeminterface associated with the second system. For example, the systeminterface may correspond to a website, an application (e.g., a mobileapplication), software, etc. associated with the second system.Alternatively and/or additionally, the system interface may be providedby the second system. In some examples, the system interface may displaya first selectable input associated with providing the second systemwith access to the first set of resources. Alternatively and/oradditionally, the first selectable input may be associated with linkingthe second system with the first email account (and/or the first useraccount). Alternatively and/or additionally, the first selectable inputmay be associated with enabling the second system to perform operationsassociated with the first email account (and/or the first user account)on behalf of the first user. Alternatively and/or additionally, thefirst selectable input may be associated with logging into the secondsystem using the content system and/or the first email account (and/orthe first user account).

Alternatively and/or additionally, the first request may be receivedusing one or more of the email interface of the one or more interfacesassociated with the content system, the communication interface of theone or more interfaces associated with the content system, the socialmedia interface of the one or more interfaces associated with thecontent system, the scheduling interface of the one or more interfacesassociated with the content system, the search interface of the one ormore interfaces associated with the content system, the news contentinterface of the one or more interfaces associated with the contentsystem, the media platform interface of the one or more interfacesassociated with the content system, etc. In some examples, a secondselectable input associated with providing the second system with accessto the first set of resources may be displayed via an interface of theone or more interfaces associated with the content system. Alternativelyand/or additionally, the second selectable input may be associated withlinking the second system with the first email account (and/or the firstuser account). Alternatively and/or additionally, the second selectableinput may be associated with enabling the second system to performoperations associated with the first email account (and/or the firstuser account) on behalf of the first user. Alternatively and/oradditionally, the second selectable input may be associated with logginginto the second system using the content system and/or the first emailaccount (and/or the first user account).

In some examples, content accessed via the interface of the one or moreinterfaces may be analyzed to determine that subject matter associatedwith the content matches and/or is related to the second system and/orto one or more services provided by the second system. The secondselectable input may be displayed based upon a determination that thesubject matter associated with the content matches and/or is related tothe second system and/or one or more services provided by the secondsystem. Alternatively and/or additionally, a content item (e.g., anadvertisement, a selectable graphical object, etc.) comprising thesecond selectable input may be displayed based upon the determinationthat the subject matter associated with the content matches and/or isrelated to the second system and/or to one or more services provided bythe second system.

In an example, the second system may be associated with a priceprotection system associated with analyzing purchase informationassociated with users to obtain refunds and/or compensation responsiveto price reductions associated with purchased products. The secondselectable input and/or the content item comprising the secondselectable input may be displayed by the email interface responsive toan email comprising purchase information (e.g., a purchase confirmation,a purchase receipt, etc.) being accessed via the email interface and/orbeing received by the first email account. Alternatively and/oradditionally, the second selectable input and/or the content itemcomprising the second selectable input may be displayed by the searchinterface responsive to identifying a query inputted into the searchinterface that is related to the price protection system (e.g., thequery may comprise one or more keywords associated with the priceprotection system, such as one or more of “refund”, “price protection”,“low prices”, “low price guarantee”, etc.). Alternatively and/oradditionally, the second selectable input and/or the content itemcomprising the second selectable input may be displayed by the mediaplatform interface responsive to identifying content (e.g., a video)accessed via the media platform interface that is related to the priceprotection system (e.g., the content may be a video discussing priceprotection rules).

In some examples, responsive to a selection of the first selectableinput and/or the second selectable input, a permission request may bereceived from the second system (and/or a server associated with thesecond system) by the content system (and/or by a server associated withthe content system). In some examples, the permission request maycorrespond to a request for a request token. Responsive to receiving thepermission request from the second system, the content system maytransmit the request token to the second system and/or to the firstclient device. For example, the request token may be stored in memory ofa server associated with the second system and/or in memory of the firstclient device. Alternatively and/or additionally, the request token maybe stored in a cookie (associated with a browser of the first clientdevice, for example).

Alternatively and/or additionally, responsive to receiving thepermission request from the second system, the content system maytransmit a token secret to the second system and/or to the first clientdevice. In some examples, the token secret may be used by the contentsystem in association with the request token to prevent one or more offorgery, hacking, etc. In some examples, the token secret may be storedin memory of a server associated with the second system and/or in memoryof the first client device. Alternatively and/or additionally, the tokensecret may be stored in the cookie.

In some examples, the first client device may be redirected to anauthorization interface associated with the content system. Theauthorization interface may correspond to an authorization web pageassociated with the content system (e.g., the authorization web page maybe provided by the content system). For example, a web address (e.g., auniform resource locator (URL)) may be used to access the authorizationinterface. In some examples, the web address may be generated based uponthe request token. For example, the web address may comprise anindication of the request token.

In some examples, the authorization interface may display a logininterface. For example, login information, such as the first emailaddress (and/or the first username associated with the first useraccount) and/or a password associated with the first email account(and/or the first user account), may be input into the login interface.For example, the login information may be received from the first clientdevice via the login interface of the authorization interface. Forexample, an authentication process may be performed using the logininterface to verify an identity of the first user (e.g., to verify thatthe first user interacting with the login interface is associated withthe first email account). In some examples, the authentication processmay be performed using the login information, a two-step verificationprocess, a multi-factor authentication (MFA) process, a single-factorauthentication process and/or a different type of authenticationprocess.

In some examples, responsive to receiving the login information and/orresponsive to performing the authentication process, a consent interfacemay be displayed (e.g., the consent interface may be displayed by theauthorization interface). In some examples, the consent interface maycomprise a scope message indicative of an access scope associated withthe first request to provide the second system with access to the firstset of resources. In some examples, the access scope may be determined(by the content system) based upon the permission request.

In some examples, the access scope may be indicative of one or morefirst types of resource access associated with the first request. Forexample, a first type of resource access may correspond to readingemails composed using the first email account (e.g., the first type ofresource access may be associated with enabling the second system toaccess, consume and/or analyze emails composed using the first emailaccount). Alternatively and/or additionally, a second type of resourceaccess may correspond to reading emails received by the first emailaccount (e.g., the second type of resource access may be associated withenabling the second system to access, consume and/or analyze emailsreceived by the first email account). Alternatively and/or additionally,a third type of resource access may correspond to reading emailsassociated with the first email account that are associated with one ormore first types of emails (e.g., the third type of resource access maybe associated with enabling the second system to access, consume and/oranalyze emails associated the first email account that are associatedwith the one or more first types of emails). For example, the one ormore first types of emails may correspond to one or more of emailscomprising payment information (e.g., purchase receipts, purchaseconfirmations, etc.), emails comprising advertisement material, emailsassociated with subscriptions, etc. Alternatively and/or additionally, afifth type of resource access may correspond to composing and/ortransmitting emails from the first email account (and/or on behalf ofthe first user) to one or more other email accounts (e.g., the emailsmay be transmitted having sender addresses indicative of the first emailaddress). Alternatively and/or additionally, a sixth type of resourceaccess may correspond to deleting emails associated with the first emailaccount (e.g., the sixth type of resource access may be associated withenabling the second system to delete emails associated with the firstemail account).

Alternatively and/or additionally, a seventh type of resource access maycorrespond to reading social media posts composed and/or posted usingthe first user account (e.g., the seventh type of resource access may beassociated with enabling the second system to access, consume and/oranalyze social media posts associated with the first user account).Alternatively and/or additionally, an eighth type of resource access maycorrespond to reading social media posts that are accessible via thefirst user account (e.g., the eighth type of resource access may beassociated with enabling the second system to access, consume and/oranalyze social media posts that are accessible via the first useraccount). Alternatively and/or additionally, a ninth type of resourceaccess may correspond to composing and/or posting social media postsusing the first user account (and/or on behalf of the first user and/orthe first user account). Alternatively and/or additionally, a tenth typeof resource access may correspond to deleting social media postsassociated with the first user account (e.g., the tenth type of resourceaccess may be associated with enabling the second system to deletesocial media posts associated with the first user account).

Alternatively and/or additionally, an eleventh type of resource accessmay correspond to reading messages composed and/or transmitted using thefirst user account (e.g., the eleventh type of resource access may beassociated with enabling the second system to access, consume and/oranalyze messages composed and/or transmitted by the first user account).Alternatively and/or additionally, a twelfth type of resource access maycorrespond to reading messages received using the first user account(e.g., the twelfth type of resource access may be associated withenabling the second system to access, consume and/or analyze messagesreceived by the first user account). Alternatively and/or additionally,a thirteenth type of resource access may correspond to composing and/ortransmitting messages from the first user account (and/or on behalf ofthe first user and/or the first user account) to one or more other useraccounts. Alternatively and/or additionally, a fourteenth type ofresource access may correspond to deleting messages associated with thefirst user account (e.g., the fourteenth type of resource access may beassociated with enabling the second system to delete messages associatedwith the first user account).

Alternatively and/or additionally, a fifteenth type of resource accessmay correspond to reading schedule information (e.g., one or moreevents, occasions, meetings, etc.) associated with the schedulinginterface and/or the electronic calendar associated with the first useraccount. Alternatively and/or additionally, a sixteenth type of resourceaccess may correspond to generating and/or adding one or more of events,occasions, meetings, etc. to the electronic calendar associated with thefirst user account (on behalf of the first user and/or the first useraccount). Alternatively and/or additionally, a seventeenth type ofresource access may correspond to reading search history associated withthe search interface (e.g., the seventeenth type of resource access maybe associated with enabling the second system to access the searchhistory). Alternatively and/or additionally, an eighteenth type ofresource access may correspond to accessing activity informationassociated with the media platform interface (e.g., the eighteenth typeof resource access may be associated with enabling the second system toaccess and/or determine videos, audio, articles, etc. accessed by thefirst user account).

In some examples, the consent interface may comprise a third selectableinput associated with providing the second system with access to thefirst set of resources (e.g., the third selectable input may beassociated with providing the second system with access to resourcesassociated with the access scope). For example, a selection of the thirdselectable input may be indicative of (and/or interpreted as) consent ofthe first user to provide the second system with access to resourcesassociated with the access scope. In some examples, responsive to aselection of the third selectable input, the request token may beauthorized (by the content system) and/or the second system may begranted access to the first set of resources (e.g., the second systemmay be granted access to resources associated with the access scope).

In some examples, the first request to provide the second system withaccess to the first set of resources may be received by the contentsystem after the selection of the third selectable input (and/or beforethe selection of the third selectable input). Alternatively and/oradditionally, the first request to provide the second system with accessto the first set of resources may be received after the request token isauthorized (and/or before the request token is authorized).Alternatively and/or additionally, the first request may comprise therequest token and/or the token secret.

In some examples, an access message may be transmitted to the secondsystem (by the content system). For example, the access message may betransmitted to the second system responsive to receiving the firstrequest. Alternatively and/or additionally, the access message may betransmitted to the second system responsive to receiving the requesttoken and/or the token secret and/or determining that the request tokenis authorized. In some examples, the access message may comprise anaccess token and/or an access secret. Alternatively and/or additionally,the access token and/or the access secret may be used by the secondsystem to access the first set of resources (and/or resources associatedwith the access scope).

At 404, a first DEA associated with the first email account may begenerated. For example, the first DEA may be generated responsive toreceiving the first request to provide the second system with access tothe one or more first resources. In some examples, the first DEA may begenerated based upon the first email address associated with the firstemail account (and/or the first username associated with the first emailaccount). For example, a portion of the first email address may bereplaced with one or more characters (e.g., the first email address maybe “jillhiggins@exampleemail.com” and/or the first DEA may be“4302higgins@exampleemail.com”, “jillhig305@exampleemail.com”,ji303iggins@exampleemail.com”, etc.). Alternatively and/or additionally,one or more characters may be added to the first email address (e.g.,the first email address may be “jillhiggins@exampleemail.com” and/or thefirst DEA may be “3928jillhiggins@exampleemail.com”,“jillhiggins4032@exampleemail.com”, etc.). Alternatively and/oradditionally, the first DEA may comprise a (random) sequence ofcharacters (e.g., letters, words and/or symbols) (e.g., the first DEAmay be “k034950@exampleemail.com”). In some examples, the first DEA maybe connected to the first email account via Internet Message AccessProtocol (IMAP)-In.

At 406, the first DEA may be transmitted to the second system. In someexamples, the first DEA may be transmitted to the second system via theaccess message (e.g., the access message may comprise the first DEA, theaccess token and/or the access secret). Alternatively and/oradditionally, the first DEA may be transmitted to the second systemseparately from the access message. In some examples, firstidentification information associated with the first email account(and/or the first user account) may be generated. The firstidentification information may comprise the first DEA, a name of thefirst user (and/or a name associated with the first email account and/orthe first user account) and/or a profile picture associated with thefirst email account and/or the first user account. In some examples, thefirst identification information may be transmitted to the second systemvia the access message (e.g., the access message may comprise the firstidentification information comprising the first DEA, the access tokenand/or the access secret). Alternatively and/or additionally, the firstidentification message may be transmitted to the second systemseparately from the access message.

In some examples, the first DEA may be generated and/or transmitted tothe second system based upon a selection of a fourth selectable inputassociated with sharing a DEA, rather than the first email address, withthe second system. For example, the first DEA, rather than the firstemail address, may be included in the first identification informationbased upon (and/or responsive to) the selection of the fourth selectableinput. For example, the authorization interface and/or the consentinterface (and/or a different interface) may comprise the fourthselectable input and/or a fifth selectable input. The fifth selectableinput may be associated with sharing the first email address with thesecond system. For example, responsive to a selection of the fifthselectable input, the first email address may be transmitted to thesecond system (e.g., the first email address may be included in thefirst identification information responsive to the selection of thefifth selectable input). Alternatively and/or additionally, responsiveto the selection of the fifth selectable input, the first DEA may not begenerated and/or transmitted to the second system.

Alternatively and/or additionally, the first DEA may be generated and/ortransmitted to the second system (automatically). For example, the firstDEA may be generated and/or transmitted to the second system based upona determination that the second system is associated with a first levelof access. For example, the second system may be identified and/ordetermined based upon the permission request. A system database may beanalyzed based upon the second system to determine a level of accessassociated with the second system. The system database may be indicativeof a plurality of systems associated with the content system and/or aplurality of levels of access associated with the plurality of systems.For example, a system of the plurality of systems may be tagged with anindication of a level of access of the plurality of levels of access.

In some examples, first systems (of the plurality of systems) associatedwith the first level of access may be associated with sharing (merely)DEAs associated with email accounts (and/or user accounts) with thefirst systems (e.g., but not sharing original and/or authentic emailaddresses associated with the email accounts). Alternatively and/oradditionally, second systems (of the plurality of systems) associatedwith a second level of access may be associated with sharing (originaland/or authentic) email addresses associated with email accounts (and/oruser accounts) with the second systems. In some examples, the firstsystems may be determined to be associated with the first level ofaccess based upon an amount of compensation received from entitiesassociated with the first systems. For example, a first exemplary systemof the first systems (such as the second system) may be determined to beassociated with the first level of access if an amount of compensation(e.g., a payment amount) received from an entity associated with thefirst exemplary system does not meet a compensation threshold.Alternatively and/or additionally, a second exemplary system of thesecond systems may be determined to be associated with the second levelof access if an amount of compensation received from an entityassociated with the second exemplary system meets the compensationthreshold.

In some examples, the first request may correspond to a request for thesecond system to be provided with user information (e.g., the firstidentification information) for purposes of logging the first clientdevice and/or the system interface into the second system. For example,the first set of resources may (merely) comprise the firstidentification information. For example, the first identificationinformation and/or the first DEA may be used by the second system to logthe first client device and/or the system interface into the secondsystem. Alternatively and/or additionally, the first identificationinformation and/or the first DEA may be used by the second system tocreate an account associated with the second system for the first user.

At 408, emails of the first email account may be analyzed to identify afirst set of emails (e.g., a set of one or more emails) associated withthe first request (and/or associated with the access scope). Forexample, the first set of emails may be determined to be associated withthe access scope and/or the one or more first types of resource accessassociated with the first request. Responsive to the one or more firsttypes of resource access of the access scope comprising the first typeof resource access (associated with emails composed using the firstemail account), one or more emails of the first set of emails may beidentified (and/or included in the first set of emails) based upon adetermination that the one or more emails are composed and/ortransmitted using the first email account. Alternatively and/oradditionally, responsive to the one or more first types of resourceaccess of the access scope comprising the second type of resource access(associated with emails received by the first email account), one ormore emails of the first set of emails may be identified (and/orincluded in the first set of emails) based upon a determination that theone or more emails are received by the first email account.Alternatively and/or additionally, responsive to the one or more firsttypes of resource access of the access scope comprising the third typeof resource access (associated with emails that are associated with theone or more first types of emails), one or more emails of the first setof emails may be identified (and/or included in the first set of emails)based upon a determination that the one or more emails are associatedwith the one or more first types of emails. Alternatively and/oradditionally, responsive to the access scope being associated withaccess to emails associated with the first email account, the first setof emails may comprise emails associated with the first email account(e.g., the first set of emails may comprise every email transmittedand/or received by the first email account).

Alternatively and/or additionally, in an example where the access scopeand/or the one or more first types of resource access associated withthe first request are associated with social media posts of the firstuser account, social media posts associated with the first user accountmay be analyzed to identify a first set of social media posts (e.g., aset of one or more social media posts) associated with the first request(and/or associated with the access scope). For example, the first set ofsocial media posts may be determined to be associated with the accessscope and/or the one or more first types of resource access associatedwith the first request. Responsive to the one or more first types ofresource access of the access scope comprising the seventh type ofresource access (associated with social media posts composed and/orposted using the first user account), one or more social media posts ofthe first set of social media posts may be identified (and/or includedin the first set of social media posts) based upon a determination thatthe one or more social media posts are composed and/or posted using thefirst user account. Alternatively and/or additionally, responsive to theone or more first types of resource access of the access scopecomprising the eighth type of resource access (associated with socialmedia posts accessible by the first user account), one or more socialmedia posts of the first set of social media posts may be identified(and/or included in the first set of social media posts) based upon adetermination that the one or more social media posts are accessible viathe first user account.

Alternatively and/or additionally, in an example where the access scopeand/or the one or more first types of resource access associated withthe first request are associated with messages of the first useraccount, messages associated with the first user account may be analyzedto identify a first set of messages (e.g., a set of one or moremessages) associated with the first request (and/or associated with theaccess scope). For example, the first set of messages may be determinedto be associated with the access scope and/or the one or more firsttypes of resource access associated with the first request. Responsiveto the one or more first types of resource access of the access scopecomprising the eleventh type of resource access (associated withmessages composed and/or transmitted using the first user account), oneor more messages of the first set of messages may be identified (and/orincluded in the first set of messages) based upon a determination thatthe one or more messages are composed and/or transmitted using the firstuser account. Alternatively and/or additionally, responsive to the oneor more first types of resource access of the access scope comprisingthe twelfth type of resource access (associated with messages receivedby the first user account), one or more messages of the first set ofmessages may be identified (and/or included in the first set ofmessages) based upon a determination that the one or more messages arereceived by the first user account. Alternatively and/or additionally,responsive to the access scope being associated with access to messagesassociated with the first user account, the first set of messages maycomprise messages associated with the first user account (e.g., thefirst set of messages may comprise every message transmitted and/orreceived by the first user account).

At 410, a first set of modified emails may be generated based upon thefirst set of emails. In some examples, a modified email of the first setof modified emails may comprise an indication of the first DEA. In someexamples, one or more first emails of the first set of emails maycorrespond to emails received by the first email account. One or morefirst modified emails of the first set of modified emails may begenerated based upon the one or more first emails of the first set ofemails. Alternatively and/or additionally, one or more second emails ofthe first set of emails may correspond to emails transmitted by thefirst email account. One or more second modified emails of the first setof modified emails may be generated based upon the one or more secondemails of the first set of emails.

In some examples, a first modified email of the one or more firstmodified emails may be generated based upon a first email of the one ormore first emails (received by the first email account). In someexamples, one or more indications of the first email address may beremoved from the first email to generate the first modified email.Alternatively and/or additionally, the first modified email may compriseone or more indications of the first DEA.

For example, the first email may comprise one or more indications of thefirst email address associated with the first email account. Forexample, the one or more indications of the first email address may becomprised within a first email header of the first email. For example,the first email header of the first email may comprise a first pluralityof email header fields, such as a first sender address field, a firstsubject field, a first date field, a first recipient address field, afirst return-path field, a first delivery date field, etc. For example,the first recipient address field may be indicative of a recipient ofthe first email and/or may comprise the first email address and/or arecipient name (e.g., the first recipient email address field maycomprise “To: Jill Higgins <jillhiggins@exampleemail.com>”).Alternatively and/or additionally, the first email may comprise a firstemail body. For example, the first email body may comprise content, suchas one or more of text, one or more images, one or more attachments,etc.

In some examples, a second email body of the first modified email may begenerated based upon the first email body of the first email. Forexample, the second email body of the first modified email may comprisethe content of the first email body. Alternatively and/or additionally,a second email header of the first modified email may be generated basedupon the first email header of the first email. In some examples, asecond plurality of email header fields, such as one or more of a secondsender address field, a second subject field, a second date field, asecond recipient address field, a second return-path field, a seconddelivery date field, etc. may be generated based upon the firstplurality of email header fields and/or the first DEA. For example, thesecond recipient email address field of the first modified email maycomprise the first DEA (e.g., the second recipient email address fieldmay comprise “To: Jill Higgins <k034950@exampleemail.com>” and/or “To:<k034950@exampleemail.com>”). Alternatively and/or additionally, thesecond sender address field of the first modified email may be the sameas the first sender address field of the first email. Alternativelyand/or additionally, the second subject field of the first modifiedemail may be the same as the first subject field of the first email.Alternatively and/or additionally, the second date field of the firstmodified email may be the same as the first date field of the firstemail. Alternatively and/or additionally, the second return-path fieldof the first modified email may be the same as the first return-pathfield of the first email. Alternatively and/or additionally, the seconddelivery date field of the first modified email may be the same as thefirst delivery date field of the first email.

In some examples, a second modified email of the one or more secondmodified emails may be generated based upon a second email of the one ormore second emails (transmitted by the first email account). In someexamples, one or more indications of the first email address may beremoved from the second email to generate the second modified email.Alternatively and/or additionally, the second modified email maycomprise one or more indications of the first DEA.

For example, the second email may comprise one or more indications ofthe first email address associated with the first email account. Forexample, the one or more indications of the first email address may becomprised within a third email header of the second email. For example,the third email header of the second email may comprise a thirdplurality of email header fields, such as a third sender address field,a third subject field, a third date field, a third recipient addressfield, a third return-path field, a third delivery date field, etc. Forexample, the third sender address field may be indicative of a sender ofthe second email and/or may comprise the first email address and/or asender name (e.g., the third email address field may comprise “From:Jill Higgins <jillhiggins@exampleemail.com>”). Alternatively and/oradditionally, the third return-path field may be indicative of an emailaddress for return mail (e.g., “Reply-To:”) and/or may comprise thefirst email address (and/or a different email address) (e.g., the thirdreturn-path field may comprise “Return-Path:<jillhiggins@exampleemail.com>”). Alternatively and/or additionally, thesecond email may comprise a third email body. For example, the thirdemail body may comprise content, such as one or more of text, one ormore images, one or more attachments, etc.

In some examples, a fourth email body of the second modified email maybe generated based upon the third email body of the second email. Forexample, the fourth email body of the second modified email may comprisethe content of the third email body. Alternatively and/or additionally,a fourth email header of the second modified email may be generatedbased upon the third email header of the second email. In some examples,a fourth plurality of email header fields, such as one or more of afourth sender address field, a fourth subject field, a fourth datefield, a fourth recipient address field, a fourth return-path field, afourth delivery date field, etc. may be generated based upon the thirdplurality of email header fields and/or the first DEA. For example, thefourth sender email address field of the second modified email maycomprise the first DEA (e.g., the fourth sender email address field maycomprise “From: Jill Higgins <k034950@exampleemail.com>” and/or “From:<k034950@exampleemail.com>”). Alternatively and/or additionally, thefourth return-path field may comprise the first DEA (e.g., the fourthreturn-path field may comprise “Return-Path:<k034950@exampleemail.com>”). Alternatively and/or additionally, thefourth recipient address field of the second modified email may be thesame as the third sender address field of the second email.Alternatively and/or additionally, the fourth subject field of thesecond modified email may be the same as the third subject field of thesecond email. Alternatively and/or additionally, the fourth date fieldof the second modified email may be the same as the third date field ofthe second email. Alternatively and/or additionally, the fourth deliverydate field of the second modified email may be the same as the thirddelivery date field of the second email.

In the example where the access scope and/or the one or more first typesof resource access associated with the first request are associated withsocial media posts of the first user account, a first set of modifiedsocial media posts may be generated based upon the first set of socialmedia posts. For example, indications of the first user account may beremoved from the first set of social media posts to generate the firstset of modified social media posts (e.g., indications of the firstusername and/or indications of the first email address may be removedfrom the first set of social media posts to generate the first set ofmodified social media posts). Alternatively and/or additionally,indications of the first DEA may be added to the first set of socialmedia posts to generate the first set of modified social media posts.

In the example where the access scope and/or the one or more first typesof resource access associated with the first request are associated withmessages of the first user account, a first set of modified messages maybe generated based upon the first set of messages. For example,indications of the first user account may be removed from the first setof messages to generate the first set of modified messages (e.g.,indications of the first username and/or indications of the first emailaddress may be removed from the first set of messages to generate thefirst set of modified messages). Alternatively and/or additionally,indications of the first DEA may be added to the first set of messagesto generate the first set of modified messages.

At 412, access to the first set of modified emails may be provided tothe second system. For example, the first set of modified emails may betransmitted to the second system (e.g., the first set of modified emailsmay be transmitted to a server associated with the second system). Insome examples, the first set of modified emails may be generated and/oraccess to the first set of modified emails may be provided to the secondsystem responsive to receiving the first request (and/or responsive toreceiving a different request comprising the access token and/or theaccess secret).

In the example where the access scope and/or the one or more first typesof resource access associated with the first request are associated withsocial media posts of the first user account, access to the first set ofmodified social media posts may be provided to the second system. Forexample, the first set of modified social media posts may be transmittedto the second system. Alternatively and/or additionally, in an examplewhere the first set of social media posts do not comprise indications ofthe first email account and/or indications of the first username, accessto the first set of social media posts may be provided to the secondsystem (and/or the first set of modified social media posts may not begenerated).

In the example where the access scope and/or the one or more first typesof resource access associated with the first request are associated withmessages of the first user account, access to the first set of modifiedmessages may be provided to the second system. For example, the firstset of modified messages may be transmitted to the second system.Alternatively and/or additionally, in an example where the first set ofmessages do not comprise indications of the first email account and/orindications of the first username, access to the first set of messagesmay be provided to the second system (and/or the first set of modifiedmessages may not be generated).

In some examples, the access scope and/or the first set of resources maybe associated with composing and/or transmitting emails from the firstemail account (and/or on behalf of the first user) to one or more otheremail accounts. For example, the one or more first types of resourceaccess of the access scope may comprise the fifth type of resourceaccess. One or more transmission emails, composed and/or transmitted bythe second system (on behalf of the first user), may be received (e.g.,the one or more transmission emails may be received by the email serviceprovider associated with the content system). In some examples, the oneor more transmission emails may be indicative of the first DEA and/ormay be addressed to one or more email addresses associated with one ormore email accounts.

At 414, a fifth email (of the one or more transmission emails) may bereceived from the second system. In some examples, the fifth email maybe addressed to a second email address associated with a second emailaccount. Alternatively and/or additionally, the fifth email may beindicative of the first DEA. For example, a fifth email header of thefifth email may comprise one or more indications of the first DEA. Insome examples, the fifth email header of the fifth email may comprise afifth plurality of email header fields, such as a fifth sender addressfield, a fifth subject field, a fifth date field, a fifth recipientaddress field, a fifth return-path field, a fifth delivery date field,etc. For example, the fifth sender address field may be indicative of asender of the fifth email and/or may comprise the first DEA and/or asender name (e.g., the third email address field may comprise “From:Jill Higgins <k034950@exampleemail.com>” and/or “From:<k034950@exampleemail.com>”). Alternatively and/or additionally, thefifth return-path field may be indicative of an email address for returnmail (e.g., “Reply-To:”) and/or may comprise the first DEA (and/or adifferent email address) (e.g., the fifth return-path field may comprise“Return-Path: <k034950@exampleemail.com>”). Alternatively and/oradditionally, the fifth email may comprise a fifth email body. Forexample, the fifth email body may comprise content, such as one or moreof text, one or more images, one or more attachments, etc.

At 416, a sixth email may be generated based upon the fifth email. Forexample, the sixth email may be indicative of the first email address.In some examples, a sixth email body of the sixth email may be generatedbased upon the fifth email body of the fifth email. For example, thesixth email body of the sixth email may comprise the content of thefifth email body. Alternatively and/or additionally, a sixth emailheader of the sixth email may be generated based upon the fifth emailheader of the fifth email. In some examples, a sixth plurality of emailheader fields, such as one or more of a sixth sender address field, asixth subject field, a sixth date field, a sixth recipient addressfield, a sixth return-path field, a sixth delivery date field, etc. maybe generated based upon the fifth plurality of email header fieldsand/or the first email address. For example, the sixth sender emailaddress field of the sixth email may comprise the first email address(e.g., the sixth sender email address field may comprise “From: JillHiggins <jillhiggins@exampleemail.com>” and/or “From:<jillhiggins@exampleemail.com>”). Alternatively and/or additionally, thesixth return-path field may comprise the first email address (e.g., thesixth return-path field may comprise “Return-Path:<jillhiggins@exampleemail.com>”). Alternatively and/or additionally, thesixth recipient address field of the sixth email may be the same as thefifth sender address field of the fifth email. For example, the fifthrecipient address field of the fifth email and/or the sixth recipientaddress field of the sixth email may comprise the second email address.Alternatively and/or additionally, the sixth subject field of the sixthemail may be the same as the fifth subject field of the fifth email.Alternatively and/or additionally, the sixth date field of the sixthemail may be the same as the fifth date field of the fifth email.Alternatively and/or additionally, the sixth delivery date field of thesixth email may be the same as the fifth delivery date field of thefifth email.

At 418, the sixth email may be transmitted to the second email accountassociated with the second email address (by the content system). In theexample where the second system is associated with the price protectionsystem, the fifth email may comprise an indication of a price reductionof a purchased product and/or a request for compensation associated withthe price reduction. Alternatively and/or additionally, the second emailaddress and/or the second email account may be associated with a firstentity (e.g., a credit card servicer, a company, etc.) responsible forreimbursing the first user and/or a price protection entity associatedwith the second system in association with the request for compensationand/or the price reduction.

In some examples, the access scope and/or the first set of resources maynot be associated with composing and/or transmitting emails from thefirst email account (and/or on behalf of the first user) to one or moreother email accounts. For example, the one or more first types ofresource access of the access scope may not comprise the fifth type ofresource access. Responsive to receiving the fifth email (and/or adifferent email of the one or more transmission emails), the accessscope may be analyzed to determine that the access scope and/or thefirst set of resources are not associated with composing and/ortransmitting emails from the first email account (and/or on behalf ofthe first user). For example, responsive to determining that the accessscope and/or the first set of resources are not associated withcomposing and/or transmitting emails from the first email account(and/or on behalf of the first user), the fifth email may be discardedand/or the sixth email may not be generated and/or transmitted to thesecond email account.

In some examples, a seventh email addressed to the first DEA may bereceived from a third email account associated with a third emailaddress. The third email account and/or the third email address may beassociated with the second system. Alternatively and/or additionally,the seventh email may be received from the second system. In someexamples, a seventh email header of the seventh email may comprise oneor more indications of the first DEA. For example, the seventh emailheader of the seventh email may comprise a seventh plurality of emailheader fields, such as a seventh sender address field, a seventh subjectfield, a seventh date field, a seventh recipient address field, aseventh return-path field, a seventh delivery date field, etc. Forexample, the seventh recipient address field may be indicative of arecipient of the first email and/or may comprise the seventh emailaddress and/or a recipient name (e.g., the seventh recipient emailaddress field may comprise “To: Jill Higgins <k034950@exampleemail.com>”and/or “To: <k034950@exampleemail.com>”). Alternatively and/oradditionally, the seventh email may comprise a seventh email body. Forexample, the seventh email body may comprise content, such as one ormore of text, one or more images, one or more attachments, etc.

In some examples, the seventh email may be transmitted to the firstemail account. For example, the seventh email may be transmitted to thefirst email account based upon a determination that the first DEA isactive (and/or is not deactivated). Alternatively and/or additionally,the seventh email may be transmitted to the first email account basedupon a determination that the first DEA is associated with the firstemail account. For example, a DEA database may be analyzed based uponthe first DEA to identify the first email account. For example, the DEAdatabase may comprise a plurality of DEAs. A DEA of the plurality ofDEAs may be associated with an email account of a plurality of emailaccounts associated with the content system. Alternatively and/oradditionally, a DEA of the plurality of DEAs may be associated with auser account of a plurality of user accounts associated with the contentsystem. For example, a DEA of the plurality of DEAs may be tagged withan indication of an email account of the plurality of email accounts.Alternatively and/or additionally, a DEA of the plurality of DEAs may betagged with an indication of a user account of the plurality of useraccounts. The DEA database may be analyzed based upon the first DEA. Theseventh email may be transmitted to the first email account responsiveto identifying the first DEA and/or determining that the first DEA istagged with an indication of the first email account.

Alternatively and/or additionally, a DEA of the plurality of DEAs may betagged with a status tag. For example, a status tag may be indicative ofa status of a corresponding DEA. For example, a status tag may beindicative of a DEA being associated with an active status where emailsaddressed to the DEA are transmitted to an email account correspondingto the DEA. Alternatively and/or additionally, a status tag may beindicative of a DEA being associated with a deactivated status whereemails addressed to the DEA are not automatically transmitted to anemail account corresponding to the DEA. For example, the seventh emailmay be transmitted to the first email account responsive to identifyingthe first DEA and/or determining that the first DEA is active. Forexample, it may be determined that the first DEA is active based upon adetermination that a first status tag associated with the first DEA isindicative of the first DEA being associated with an active status.

Alternatively and/or additionally, an eighth email may be generatedbased upon the seventh email. For example, an eighth email body of theeighth email may be generated based upon the seventh email body of theseventh email. For example, the eighth email body of the eighth emailmay comprise the content of the seventh email body. Alternatively and/oradditionally, an eighth email header of the eighth email may begenerated based upon the seventh email header of the seventh email. Insome examples, an eighth plurality of email header fields, such as oneor more of an eighth sender address field, an eighth subject field, aneighth date field, an eighth recipient address field, an eighthreturn-path field, an eighth delivery date field, etc. may be generatedbased upon the seventh plurality of email header fields of the seventhemail and/or the first email address. For example, the eighth recipientemail address field of the eighth email may comprise the first emailaddress (e.g., the second recipient email address field may comprise“To: Jill Higgins <jillhiggins@exampleemail.com>” and/or “To:<jillhiggins@exampleemail.com>”).

In some examples, the eighth email may be transmitted to the first emailaccount. For example, the eighth email may be generated and/ortransmitted to the first email account based upon a determination thatthe first DEA is active (and/or is not deactivated). Alternativelyand/or additionally, the eighth email may be generated and/ortransmitted to the first email account based upon a determination thatthe first DEA is associated with the first email account.

Alternatively and/or additionally, in an example where the first useraccount is associated with a messaging account associated with thecommunication service and/or a social media account associated with thesocial media service, a first message may be generated based upon theseventh email. For example, the first message may comprise the contentof the seventh email. The first message may be transmitted to the firstuser account and/or to the first client device.

At 420, the first DEA may be deactivated. In some examples, deactivatingthe first DEA may be associated with changing a status of the first DEAfrom active to deactivated. For example, the first status tag associatedwith the first DEA may be modified such that rather than the firststatus tag being indicative of the first DEA being associated with theactive status, the first status tag may be indicative of the first DEAbeing associated with a deactivated status. Alternatively and/oradditionally, deactivating the first DEA may be associated with removingthe first DEA from the DEA database. Alternatively and/or additionally,deactivating the first DEA may be associated with not providing thesecond system with access to resources associated with the access scope.

In some examples, the first DEA may be deactivated responsive toreceiving a second request to deactivate the first DEA. For example, thesecond request to deactivate the first DEA may be received from thefirst client device associated with the first email account (and/or thefirst user account). Alternatively and/or additionally, the secondrequest to deactivate the first DEA may be received from a differentclient device associated with the first email account (and/or the firstuser account) (e.g., the different client device may be logged into thefirst email account and/or the first user account).

In some examples, the first client device may be used to display adeactivation interface (e.g., the deactivation interface may be a webpage associated with the content system and/or the deactivationinterface may be accessed via a notification, a message and/or an email,transmitted by the content system, to the first email account, etc.).Alternatively and/or additionally, the deactivation interface may beaccessed and/or displayed via an interface of the one or more interfacesassociated with the content system. The deactivation interface maycomprise a deactivate selectable input corresponding to requestingdeactivation of the first DEA. For example, the second request todeactivate the first DEA may be received responsive to a selection ofthe deactivate selectable input.

In some examples, a first notification may be transmitted to the firstclient device responsive to a determination that a first duration oftime that the first DEA is active (e.g., a duration of time since a timethat the first DEA was generated) meets a first threshold duration oftime (e.g., one week, one month, etc.). For example, the firstnotification may be a ninth email transmitted to the first emailaccount. Alternatively and/or additionally, the first notification maybe a message transmitted to the first user account and/or to the firstclient device. The first notification may be indicative of the firstduration of time meeting the first threshold duration of time (e.g., thefirst notification may comprise “The DEA for the price protection systemaccessing your email account was generated one month ago. Do you want todeactivate the DEA?”). Alternatively and/or additionally, the firstnotification may comprise a second deactivate selectable input.Responsive to a selection of the second deactivate selectable input, thesecond request to deactivate the first DEA may be received.

Alternatively and/or additionally, a second notification may betransmitted to the first client device responsive to a determinationthat a second duration of time of inactivity associated with the firstDEA meets a second threshold duration of time. For example, the secondduration of time of inactivity may correspond to a time in which anemail addressed to the first DEA is not received by the first emailaccount and/or the content system (e.g., 0 emails addressed to the firstDEA are received by the first email account and/or the content systemduring the second duration of time of inactivity). Alternatively and/oradditionally, the second duration of time of inactivity may correspondto a time in which one or more emails and/or one or more modified emailsassociated with the first email account are not accessed by the secondsystem. Alternatively and/or additionally, the second duration of timeof inactivity may correspond to a time in which one or more emailshaving sender addresses corresponding to the first DEA (composed and/ortransmitted on behalf of the first user) are not received by the contentsystem. Alternatively and/or additionally, the second duration of timeof inactivity may correspond to a time in which one or more resourcesassociated with the first email account and/or the first user accountare not accessed by the second system. Alternatively and/oradditionally, the second notification may be a tenth email transmittedto the first email account. Alternatively and/or additionally, thesecond notification may be a message transmitted to the first useraccount and/or to the first client device.

For example, the second notification may be indicative of the secondduration of time of inactivity meeting the second threshold duration oftime (e.g., the second notification may comprise “You haven't receivedany emails addressed to the DEA in over a month and you haven't beenusing the price protection services. Do you want to deactivate theDEA?”). The second notification may comprise a third deactivateselectable input. Responsive to a selection of the third deactivateselectable input, the second request to deactivate the first DEA may bereceived.

Alternatively and/or additionally, a third notification may betransmitted to the first client device responsive to identifying one ormore malicious emails and/or messages addressed to the first DEA. Forexample, the third notification may be an eleventh email transmitted tothe first email account. Alternatively and/or additionally, the thirdnotification may be a message transmitted to the first user accountand/or to the first client device. The one or more malicious emails maybe determined to be malicious based upon a determination that the one ormore malicious emails match one or more emails stored in a database ofmalicious emails comprising emails previously marked as being malicious.Alternatively and/or additionally, the one or more malicious emails maybe determined to be malicious based upon a determination that the one ormore malicious emails comprise links to unsecure and/or malicious webpages (e.g., blacklisted web pages). For example, the third notificationmay be indicative of the one or more malicious emails (e.g., theeleventh email may comprise “Malicious emails addressed to the DEAassociated with the Price Protection System have been identified. Itseems the DEA may be targeted by malicious entities. Do you want todeactivate the DEA?”). The third notification may comprise a fourthdeactivate selectable input. Responsive to a selection of the fourthdeactivate selectable input, the second request to deactivate the firstDEA may be received.

In some examples, the first DEA may be deactivated (automatically)responsive to the determination that the first duration of time that thefirst DEA is active is greater than the first threshold duration of time(and/or a third threshold duration of time). Alternatively and/oradditionally, the first DEA may be deactivated (automatically)responsive to the determination that second duration of time ofinactivity associated with the first DEA is greater than the secondthreshold duration of time (and/or a fourth threshold duration of time).Alternatively and/or additionally, the first DEA may be deactivated(automatically) responsive to identifying the one or more maliciousemails addressed to the first DEA and/or determining that a quantity ofmalicious emails of the one or more malicious emails is greater than athreshold quantity of malicious emails.

In some examples, a fourth notification associated with deactivation ofthe first DEA may be transmitted to a system client device associatedwith the second system. For example, the fourth notification may be atwelfth email transmitted to an email account associated with the secondsystem. Alternatively and/or additionally, the fourth notification maybe a message transmitted to the system client device. In some examples,the fourth notification may be indicative of deactivation of the firstDEA if compensation is not received from an entity associated with thesecond system (e.g., the fourth notification may comprise, “A DEA of auser account using your system will be deactivated and you will loseaccess to resources associated with the user account if you do notprovide a payment to us. Would you like to provide a payment so that theDEA is not deactivated?”). Alternatively and/or additionally, the fourthnotification may be transmitted to the system client device responsiveto a determination that DEAs associated with a second plurality of emailaccounts (and/or a plurality of user accounts) are scheduled to bedeactivated within a period of time. For example, the fourthnotification may be transmitted to the system client device responsiveto a determination that a quantity of email accounts of the secondplurality of email accounts (and/or a quantity of user accounts of theplurality of user accounts) meet a threshold quantity. Alternativelyand/or additionally, the fourth notification may be indicative ofdeactivation of the DEAs associated with the second plurality of emailaccounts (and/or the plurality of user accounts) if compensation is notreceived from an entity associated with the second system (e.g., thefourth notification may comprise, “DEAs of 110 user accounts using yoursystem will be deactivated and you will lose access to resourcesassociated with the user accounts if you do not provide a payment to us.Would you like to provide a payment so that the DEAs are notdeactivated?”). In some examples, the fourth notification may comprise asixth selectable input associated with providing a payment to (anaccount associated with) the content system. For example, responsive toreceiving a payment, the first DEA and/or the DEAs associated with thesecond plurality of email accounts (and/or the plurality of useraccounts) may not be deactivated at one or more scheduled deactivationtimes. Alternatively and/or additionally, the one or more scheduleddeactivation times may be modified based upon the payment (e.g., the oneor more scheduled deactivation times may be modified by adding a periodof time, such as one or more of a week, a month, a year, etc., to theone or more scheduled deactivation times).

In some examples, after deactivating the first DEA, a third request toaccess one or more resources associated with the access scope may bereceived from the second system. For example, the third request maycomprise the access token and/or the access secret. In some examples,the access token and/or the access secret may be associated with thefirst DEA. The third request to access one or more resources associatedwith the access scope may be denied responsive to a determination thatthe first DEA is deactivated and/or is not active (e.g., it may bedetermined that the first DEA is deactivated and/or is not active basedupon the DEA database). Alternatively and/or additionally, the accesstoken and/or the access secret may be deactivated in association withdeactivating the first DEA. For example, the third request to access oneor more resources associated with the access scope may be deniedresponsive to a determination that the access token and/or the accesssecret are deactivated.

It may be appreciated that one or more of the techniques presentedherein may be performed using a protocol, such as an OAuth protocoland/or a different protocol associated with authorizing a system to userresources associated with a user account. For example, the access tokenand/or the access secret may be generated and/or used in accordance withthe protocol. Alternatively and/or additionally, the second system maybe provided with access to one or more resources associated with thefirst email account and/or the first user account in accordance with theprotocol.

FIGS. 5A-5H illustrate examples of a system 501 for providing a systemwith access to one or more resources associated with a user accountusing a DEA. A first user, such as user Thomas, and/or a first clientdevice 500 associated with the first user may access and/or interactwith an email system for sending and/or receiving emails. For example, afirst email account of the first user with the email system may beaccessed and/or interacted with via a first email interface, such as anemail client, a web email interface accessed via a browser, an emailapplication, etc. on the first client device 500. In some examples, theemail system may be associated with an email service provider.

FIG. 5A illustrates a graphical user interface of the first clientdevice 500 being controlled to display the first email interface. Forexample, the first email interface may display a list of emails. Thelist of emails may correspond to an inbox of the first email account.The list of emails may comprise a first list item 502 corresponding to afirst email 544 (illustrated in FIG. 5B). For example, a selection ofthe first list item 502 may be received via the first email interface.

FIG. 5B illustrates the graphical user interface of the first clientdevice 500 being controlled to display the first email 544. For example,the first email 544 may be displayed responsive to the selection of thefirst list item 502 from the list of emails. In some examples, the firstemail 544 may comprise purchase information (e.g., a purchaseconfirmation, a purchase receipt, etc.) associated with a purchase bythe first user. In some examples, it may be determined that subjectmatter of the first email 544 matches and/or is related to one or moreservices provided by a price protection system associated with analyzingpurchase information associated with users to obtain refunds and/orcompensation responsive to price reductions associated with purchasedproducts.

Responsive to determining that the subject matter of the first email 544matches and/or is related to the one or more services provided by theprice protection system, a content item 508 may be displayed adjacent tothe first email 544. For example, the content item 508 may comprise aselectable input associated with providing the price protection systemwith access to one or more resources associated with the one or moreservices. Alternatively and/or additionally, the content item 508 may beassociated with linking the price protection system with the first emailaccount. Alternatively and/or additionally, the content item 508 may beassociated with enabling the price protection system to performoperations associated with the first email account on behalf of thefirst user.

In some examples, a selection of the selectable input (and/or thecontent item 508) may be received. Responsive to the selection of theselectable input (and/or the content item 508), a request token may begenerated and/or transmitted to the price protection system.Alternatively and/or additionally, responsive to the selection of theselectable input (and/or the content item 508), a token secret may begenerated and/or transmitted to the price protection system.Alternatively and/or additionally, responsive to the selection of theselectable input (and/or the content item 508), an authenticationprocess may be performed to verify an identity of the first user. Insome examples, the authentication process may be performed using logininformation received via a login interface, a two-step verificationprocess, an MFA process, a single-factor authentication process and/or adifferent type of authentication process.

FIG. 5C illustrates the graphical user interface of the first clientdevice 500 being controlled to display a consent interface 514. Forexample, the consent interface 514 may be displayed responsive to theauthentication process being performed. In some examples, the consentinterface 514 may comprise a scope message indicative of an access scopeassociated with one or more first types of resource access. For example,the access scope may be associated with reading (all) emails associatedwith the first email account, composing and/or transmitting emails usingthe first email account and/or deleting emails associated with the firstemail account. In some examples, the consent interface 514 may comprisea first selectable input 516 associated with providing the priceprotection system with access to resources associated with the accessscope. For example, a selection of the first selectable input 516 may beindicative of (and/or interpreted as) consent of the first user toprovide the price protection system with access to resources associatedwith the access scope. In some examples, responsive to a selection ofthe first selectable input 516, the request token may be authorized (bythe email system) and/or the price protection system may be grantedaccess to resources associated with the access scope.

FIG. 5D illustrates a request 526 to provide the price protection systemwith access to resources associated with the access scope beingtransmitted by a first server 528 associated with the price protectionsystem to a second server 524 associated with the email system. In someexamples, the request 526 may be transmitted to the second server 524associated with the email system after the selection of the firstselectable input 516 (and/or before the selection of the firstselectable input 516). Alternatively and/or additionally, the request526 may be transmitted to the second server 524 associated with theemail system after the after the request token is authorized (and/orbefore the request token is authorized). Alternatively and/oradditionally, the request 526 may comprise the request token and/or thetoken secret.

In some examples, an access message may be transmitted to the firstserver 528 associated with the price protection system. For example, theaccess message may be transmitted to the first server 528 associatedwith the price protection system responsive to receiving the request526. Alternatively and/or additionally, the access message may betransmitted to the first server 528 associated with the price protectionsystem responsive to receiving the request token and/or the token secretand/or determining that the request token is authorized. In someexamples, the access message may comprise an access token and/or anaccess secret. Alternatively and/or additionally, the access tokenand/or the access secret may be used by the price protection system toaccess resources associated with the access scope.

In some examples, a first DEA (e.g., “6234@email.com”) associated withthe first email account may be generated. Alternatively and/oradditionally, the first DEA may be transmitted to the first server 528associated with the price protection system. In some examples, the firstDEA may be transmitted to the first server 528 associated with the priceprotection system via the access message (e.g., the access message maycomprise the first DEA, the access token and/or the access secret).Alternatively and/or additionally, the first DEA may be transmitted tothe first server 528 associated with the price protection systemseparately from the access message.

FIG. 5E illustrates a plurality of modified emails 538 being generatedbased upon a plurality of emails 534 of the first email account. Forexample, the plurality of modified emails 538 may be generated bymodifying the plurality of emails 534 using a modifier 536. In someexamples, the plurality of emails 534 may comprise indications of afirst email address (e.g., “TomB@email.com”) associated with the firstemail account. Alternatively and/or additionally, indications of thefirst email address may be removed from the plurality of emails 534 togenerate the plurality of modified emails 538. Alternatively and/oradditionally, indications of the first DEA may be added to the pluralityof emails 534 to generate the plurality of modified emails 538.

FIG. 5F illustrates a first modified email 546 of the plurality ofmodified emails 538 being generated based upon the first email 544 ofthe plurality of emails 534. In some examples, a first recipient addressfield (e.g., “TO: <TomB@email.com>”) of a first email header of thefirst email 544 may be modified to generate a second recipient addressfield (e.g., “TO: <6234@email.com>”) of a second email header of thefirst modified email 546. For example, the first email address may beremoved from the first recipient address field to generate the secondrecipient address field. Alternatively and/or additionally, the firstemail address within the first recipient address field may be replacedwith the first DEA to generate the second recipient address field of thesecond email header. Alternatively and/or additionally, a second emailbody of the first modified email 546 may be generated based upon a firstemail body of the first email 544. For example, the second email body ofthe first modified email 546 may comprise content (e.g., text, one ormore images, one or more attachments, etc.) of the first email body ofthe first email 544.

In some examples, a second email 562 (e.g., illustrated in FIG. 5H) maybe transmitted to the first email account (by the email system). Forexample, the second email 562 may be indicative of the first DEAexpiring at a first time. FIG. 5G illustrates the graphical userinterface of the first client device 500 being controlled to display thefirst email interface. The first email interface may display a secondlist of emails. The second list of emails may correspond to the inbox ofthe first email account. The second list of emails may comprise a secondlist item 552 corresponding to the second email 562. For example, aselection of the second list item 552 may be received via the firstemail interface.

FIG. 5H illustrates the graphical user interface of the first clientdevice 500 being controlled to display the second email 562. Forexample, the second email 562 may be displayed responsive to theselection of the second list item 552 from the second list of emails. Insome examples, the second email 562 may comprise a second selectableinput 558 associated with deactivating the first DEA and/or a thirdselectable input 560 associated with not deactivating the first DEA. Insome examples, a second request to deactivate the first DEA may bereceived (by the email system) via a selection of the second selectableinput 558. For example, responsive to receiving the second request, thefirst DEA may be deactivated. Alternatively and/or additionally,responsive to receiving the second request, access to resourcesassociated with the access scope may not be provided to the priceprotection system.

It may be appreciated that the disclosed subject matter may assist auser (e.g., and/or a client device associated with the user) inproviding a system with access to resources associated with a first useraccount, such as a first email account, of the user without providing ausername and/or an email address (and/or other personal information) tothe systems.

Implementation of at least some of the disclosed subject matter may leadto benefits including, but not limited to, a reduction in screen spaceand/or an improved usability of a display (of the client device) (e.g.,as a result of generating a DEA corresponding to a first user account,as a result of using the DEA, rather than the email address and/or theusername associated with the first user account for providing resourcesto a system, wherein the user may not be required to disclose the emailaddress and/or the username associated with the first user account,wherein entities may be prevented from sending unwanted and/orundesirable emails and/or messages to the first user account bydeactivating the DEA, wherein the user may not need to scroll throughunwanted and/or undesirable emails and/or messages to consume(desirable) emails and/or messages, etc.).

Alternatively and/or additionally, implementation of at least some ofthe disclosed subject matter may lead to benefits including a reductionin bandwidth (e.g., as a result of preventing entities from sendingunwanted and/or undesirable emails and/or messages to the first useraccount by deactivating the DEA, such that the unwanted and/orundesirable emails and/or messages are not downloaded to the clientdevice).

Alternatively and/or additionally, implementation of at least some ofthe disclosed subject matter may lead to benefits including moreaccurate and precise transmission of content to intended users (e.g., asa result of preventing entities from sending unwanted and/or undesirableemails and/or messages to the first user account by deactivating theDEA, such that the unwanted and/or undesirable emails and/or messagesare not downloaded to the client device and/or merely wanted and/ordesirable emails and/or messages may be sent to the first user accountand/or downloaded to the client device).

Alternatively and/or additionally, implementation of at least some ofthe disclosed subject matter may lead to benefits including a fasterloading of content on a receiving device. For example, by reducingundesirable emails and/or messages transmitted to the first user accountand/or by reducing undesirable content associated with the undesirableemails and/or messages downloaded to the client device, as provided forherein, content may be downloaded to the client device at an increasedspeed, and thus delay between a determination to transmit content andcompletion of transmission of the content and/or presenting of thecontent can be reduced.

Alternatively and/or additionally, implementation of at least some ofthe disclosed subject matter may lead to benefits including protectinguser privacy and/or preventing unauthorized access to personalinformation associated with the user (e.g., as a result of providing thefirst DEA to the system rather than providing personal information suchas the email address and/or the username to the system, etc.).Alternatively and/or additionally, implementation of at least some ofthe disclosed subject matter may lead to benefits including decreasingsecurity resources needed to protect the personal information fromunauthorized access.

In some examples, at least some of the disclosed subject matter may beimplemented on a client device, and in some examples, at least some ofthe disclosed subject matter may be implemented on a server (e.g.,hosting a service accessible via a network, such as the Internet).

FIG. 6 is an illustration of a scenario 600 involving an examplenon-transitory machine readable medium 602. The non-transitory machinereadable medium 602 may comprise processor-executable instructions 612that when executed by a processor 616 cause performance (e.g., by theprocessor 616) of at least some of the provisions herein (e.g.,embodiment 614). The non-transitory machine readable medium 602 maycomprise a memory semiconductor (e.g., a semiconductor utilizing staticrandom access memory (SRAM), dynamic random access memory (DRAM), and/orsynchronous dynamic random access memory (SDRAM) technologies), aplatter of a hard disk drive, a flash memory device, or a magnetic oroptical disc (such as a compact disc (CD), digital versatile disc (DVD),or floppy disk). The example non-transitory machine readable medium 602stores computer-readable data 604 that, when subjected to reading 606 bya reader 610 of a device 608 (e.g., a read head of a hard disk drive, ora read operation invoked on a solid-state storage device), express theprocessor-executable instructions 612. In some embodiments, theprocessor-executable instructions 612, when executed, cause performanceof operations, such as at least some of the example method 400 of FIG. 4, for example. In some embodiments, the processor-executableinstructions 612 are configured to cause implementation of a system,such as at least some of the example system 501 of FIGS. 5A-5H, forexample.

3. Usage of Terms

As used in this application, “component,” “module,” “system”,“interface”, and/or the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a controller and the controller can be a component. One or morecomponents may reside within a process and/or thread of execution and acomponent may be localized on one computer and/or distributed betweentwo or more computers.

Unless specified otherwise, “first,” “second,” and/or the like are notintended to imply a temporal aspect, a spatial aspect, an ordering, etc.Rather, such terms are merely used as identifiers, names, etc. forfeatures, elements, items, etc. For example, a first object and a secondobject generally correspond to object A and object B or two different ortwo identical objects or the same object.

Moreover, “example” is used herein to mean serving as an instance,illustration, etc., and not necessarily as advantageous. As used herein,“or” is intended to mean an inclusive “or” rather than an exclusive“or”. In addition, “a” and “an” as used in this application aregenerally be construed to mean “one or more” unless specified otherwiseor clear from context to be directed to a singular form. Also, at leastone of A and B and/or the like generally means A or B or both A and B.Furthermore, to the extent that “includes”, “having”, “has”, “with”,and/or variants thereof are used in either the detailed description orthe claims, such terms are intended to be inclusive in a manner similarto the term “comprising”.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing at least some of the claims.

Furthermore, the claimed subject matter may be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. Of course, manymodifications may be made to this configuration without departing fromthe scope or spirit of the claimed subject matter.

Various operations of embodiments are provided herein. In an embodiment,one or more of the operations described may constitute computer readableinstructions stored on one or more computer and/or machine readablemedia, which if executed will cause the operations to be performed. Theorder in which some or all of the operations are described should not beconstrued as to imply that these operations are necessarily orderdependent. Alternative ordering will be appreciated by one skilled inthe art having the benefit of this description. Further, it will beunderstood that not all operations are necessarily present in eachembodiment provided herein. Also, it will be understood that not alloperations are necessary in some embodiments.

Also, although the disclosure has been shown and described with respectto one or more implementations, equivalent alterations and modificationswill occur to others skilled in the art based upon a reading andunderstanding of this specification and the annexed drawings. Thedisclosure includes all such modifications and alterations and islimited only by the scope of the following claims. In particular regardto the various functions performed by the above described components(e.g., elements, resources, etc.), the terms used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., that is functionally equivalent), even though notstructurally equivalent to the disclosed structure. In addition, while aparticular feature of the disclosure may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.

What is claimed is:
 1. A method, comprising: receiving a request to provide a system with access to a first set of resources, wherein the first set of resources are associated with a first email account associated with a first email address; generating a first disposable email address (DEA) associated with the first email account; transmitting, to the system, the first DEA associated with the first email account; analyzing emails of the first email account to identify a first set of emails associated with the request to provide the system with access to the first set of resources, wherein a first email of the first set of emails comprises an indication of the first email address and a second email of the first set of emails comprises an indication of the first email address; and generating, based upon the first set of emails comprising the first email and the second email, a first set of modified emails associated with the request, wherein the generating the first set of modified emails comprises concurrently: generating a first modified email of the first set of modified emails by replacing the indication of the first email address in the first email with an indication of the first DEA; and generating a second modified email of the first set of modified emails by replacing the indication of the first email address in the second email with an indication of the first DEA.
 2. The method of claim 1, comprising: receiving a third email, addressed to the first DEA, from the system; and transmitting the third email to the first email account.
 3. The method of claim 1, comprising: receiving a third email, addressed to the first DEA, from the system; generating a fourth email based upon the third email, wherein the fourth email comprises an indication of the first email address; and transmitting the fourth email to the first email account.
 4. The method of claim 3, wherein the generating the fourth email based upon the third email comprises: generating a fourth email body of the fourth email based upon content of a third email body of the third email, wherein the fourth email body of the fourth email comprises the content of the third email body of the third email; and generating a fourth email header of the fourth email, wherein: the fourth email header comprises a sender address indicative of the first email address; and the fourth email header of the fourth email is different than a third email header of the third email.
 5. The method of claim 1, wherein the generating the first set of modified emails comprises: generating a first email body of the first modified email based upon content of a third email body of a third email of the first set of emails, wherein the first email body of the first modified email comprises the content of the third email body of the third email; and generating a first email header of the first modified email, wherein at least one of: the first email header comprises a sender address indicative of the first DEA and the first email header of the first modified email is different than a third email header of the third email; or the first email header comprises a recipient address indicative of the first DEA and the first email header of the first modified email is different than the third email header of the third email.
 6. The method of claim 2, wherein a sender address of the third email is indicative of the first DEA.
 7. The method of claim 3, wherein a sender address of the fourth email is indicative of the first email address.
 8. The method of claim 1, comprising: controlling a graphical user interface of a first client device associated with the first email account to display an interface; and displaying, via the interface, a selectable input associated with providing the system with access to the first set of resources, wherein the request is received responsive to a selection of the selectable input.
 9. The method of claim 1, wherein the request is received from a server associated with the system.
 10. The method of claim 1, comprising deactivating the first DEA.
 11. The method of claim 1, comprising: determining that a duration of time that the first DEA is active meets a threshold duration of time; generating, based upon the duration of time meeting the threshold duration of time, a notification; and transmitting the notification to a first client device associated with the first email account, wherein: the notification comprises a selectable input corresponding to deactivating the first DEA.
 12. The method of claim 1, comprising deactivating the first DEA responsive to a duration of time that the first DEA is active meeting a threshold duration of time.
 13. A computing device comprising: a processor; and memory comprising processor-executable instructions that when executed by the processor cause performance of operations, the operations comprising: receiving a request to provide a system with access to a first set of resources, wherein the first set of resources are associated with a first email account associated with a first email address; generating a first disposable email address (DEA) associated with the first email account; transmitting, to the system, the first DEA associated with the first email account; generating, based upon a first set of emails, a first set of modified emails associated with the request, wherein a first modified email of the first set of modified emails comprises an indication of the first DEA, and a second modified email of the first set of modified emails comprises an indication of the first DEA; and based upon the request, providing, to the system, access to the first set of modified emails comprising the first modified email and the second modified email.
 14. The computing device of claim 13, wherein the request is received from a server associated with the system.
 15. The computing device of claim 13, wherein the operations comprise deactivating the first DEA responsive to receiving a second request to deactivate the first DEA.
 16. The computing device of claim 13, wherein the operations comprise deactivating the first DEA responsive to a duration of time that the first DEA is active meeting a threshold duration of time.
 17. A non-transitory machine readable medium having stored thereon processor-executable instructions that when executed cause performance of operations, the operations comprising: controlling a graphical user interface of a first client device associated with a first user account to display a selectable input associated with providing a system with access to a first set of resources associated with the first user account; receiving a request to provide the system with access to the first set of resources via a selection of the selectable input; generating a first disposable email address (DEA) associated with the first user account; based upon the request, generating, based upon a first set of content items of the first user account, a first set of modified content items, wherein a first modified content item of the first set of modified content items comprises an indication of the first DEA and a second modified content item of the first set of modified content items comprises an indication of the first DEA; and providing, to the system, access to the first set of modified content items comprising the first modified content item and the second modified content item.
 18. The non-transitory machine readable medium of claim 17, wherein the first user account is associated with a first email account.
 19. The non-transitory machine readable medium of claim 17, the operations comprising: deactivating the first DEA.
 20. The non-transitory machine readable medium of claim 19, wherein the deactivating the first DEA is performed responsive to at least one of: receiving a second request to deactivate the first DEA; or a duration of time that the first DEA is active meeting a threshold duration of time. 